Method for vehicle data collection

ABSTRACT

A vehicle data collection method is disclosed. The method comprises receiving vehicle data, determining that an internet connection is not available, storing the vehicle data, determining that an internet connection has become available, and transmitting the vehicle data based at least in part on the determination that an internet connection has become available.

BACKGROUND OF THE INVENTION

Vehicle data may be used to analyze usage patterns, determine efficienttrajectories, or determine other relevant metrics. Analysis may requirea large amount of computing power and in some cases is based on vehicledata from multiple vehicles. In some instances, weight or connectivitylimitations prevent the analysis from occurring onboard the vehicle.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the invention are disclosed in the followingdetailed description and the accompanying drawings.

FIG. 1A is a diagram illustrating an embodiment of data transfer from anaircraft to a device.

FIG. 1B is a diagram illustrating an embodiment of data transfer from adevice to a network.

FIG. 2A is a flow diagram illustrating an embodiment of a flight datacollection process.

FIG. 2B is a flow diagram illustrating an embodiment of a flight datacollection process.

FIG. 2C is a flow diagram illustrating an embodiment of a flight datacollection process.

FIG. 2D is a flow diagram illustrating an embodiment of a vehicle datacollection process.

FIG. 3 is a diagram illustrating an embodiment of onboard flight datacollection elements.

FIG. 4 is a flow diagram illustrating an embodiment of user actionsthroughout a vehicle data collection process.

FIG. 5 is a diagram illustrating an embodiment of a vehicle datacollection application.

FIG. 6 is a diagram illustrating an embodiment of devices connected to anetwork.

FIG. 7 is a diagram illustrating an embodiment of a vehicle dataapplication displaying processed flight data.

FIG. 8 is a flow diagram illustrating an embodiment of a data uploadprompt process.

FIG. 9 is a diagram illustrating an embodiment of an aircraft.

DETAILED DESCRIPTION

The invention can be implemented in numerous ways, including as aprocess; an apparatus; a system; a composition of matter; a computerprogram product embodied on a computer readable storage medium; and/or aprocessor, such as a processor configured to execute instructions storedon and/or provided by a memory coupled to the processor. In thisspecification, these implementations, or any other form that theinvention may take, may be referred to as techniques. In general, theorder of the steps of disclosed processes may be altered within thescope of the invention. Unless stated otherwise, a component such as aprocessor or a memory described as being configured to perform a taskmay be implemented as a general component that is temporarily configuredto perform the task at a given time or a specific component that ismanufactured to perform the task. As used herein, the term ‘processor’refers to one or more devices, circuits, and/or processing coresconfigured to process data, such as computer program instructions.

A detailed description of one or more embodiments of the invention isprovided below along with accompanying figures that illustrate theprinciples of the invention. The invention is described in connectionwith such embodiments, but the invention is not limited to anyembodiment. The scope of the invention is limited only by the claims andthe invention encompasses numerous alternatives, modifications andequivalents. Numerous specific details are set forth in the followingdescription in order to provide a thorough understanding of theinvention. These details are provided for the purpose of example and theinvention may be practiced according to the claims without some or allof these specific details. For the purpose of clarity, technicalmaterial that is known in the technical fields related to the inventionhas not been described in detail so that the invention is notunnecessarily obscured.

A vehicle data collection method is disclosed. The method comprisesreceiving vehicle data, determining that an internet connection is notavailable, storing the vehicle data, determining that an internetconnection has become available, and transmitting the vehicle data basedat least in part on the determination that an internet connection hasbecome available. Various actions may be executed based on thedetermination of whether an internet connection is available, such asintermittent connectivity checks, prompting, or locking the vehicle.

Vehicle data may be utilized by pilots/drivers or a vehicle company tosurvey usage patterns, determine ways to improve trips, or perform otheranalysis. In some instances, vehicle data analysis cannot be performedonboard a vehicle due to computing requirements or weight constraints.Vehicle data from multiple vehicles may be desired, requiring a means ofdata congregation. However, vehicles traveling in remote areas without aWiFi or cellular connection may experience difficulties in communicatingvehicle data to another vehicle or to a shared network. In the disclosedmethod, a check is performed to determine whether an internet connectionis available, and data management is based upon the determination. Forexample, vehicle data may be relayed in real-time in the event aninternet connection is available during a trip. In the event an internetconnection is not available during the trip, vehicle data is maintaineduntil a connection is available. Data for multiple vehicles may be sentto a shared network and analyzed, with the resulting analysis providedto relevant parties.

The disclosed method may be executed by a vehicle data recording deviceof the vehicle. In some embodiments, a lower resolution data or subsetof data recorded by the recording device is desired for analysis. Thedisclosed method may be executed on a second device either installed onthe vehicle or independent of the vehicle, wherein a subset of vehicledata recording device data is transferred and stored on the seconddevice. For example, a portable device capable of being transportedindependently of the vehicle such as a smart phone, tablet, smart watch,or other internet of things (IoT) device may be used. A portable devicemay be ideal in the event the vehicle is not easily transported to alocation with an internet connection (e.g. the vehicle is an aircraftthat typically lands on water or a large truck designed for specificterrain). The disclosed method may be executed by an application capableof running on multiple platforms.

FIG. 1A is a diagram illustrating an embodiment of data transfer from anaircraft to a device. In various embodiments, the method may be used inan electric car, electric aircraft, or any appropriate vehicle. In anelectric car application, the vehicle data comprises electric car data.In an aircraft application, the vehicle data comprises flight data.

In the example shown, flight data is transferred from aircraft 100 todevice 102. The data transfer may occur following landing. In someembodiments, the data transfer occurs each time a flight is completed onaircraft 100. Flight data may be collected during flight and stored onaircraft 100 using an electronic recording device. A subset of thedetailed flight data may be transferred to device 102 in the event theelectronic recording device collects more detailed flight data than isdesired for analysis. In some embodiments, time series data and logfiles are stored onboard the aircraft. Time series data may betransferred to the device whereas the log files are not. Camera footageor audio data (e.g. from inside the fuselage) may be recorded andtransferred.

A dependable internet or cellular connection may not be available duringflight or at landing. In some embodiments, data transfer between acomputer memory (e.g. of an electronic recording device) onboard theaircraft and device 102 occurs over a wireless connection that does notrequire internet. For example, a Bluetooth connection is used or a localarea network (LAN) is generated on the aircraft. In the event a localarea network is used, device 102 receives data from a vehicle datarecording or storage device on the local area network by specifying acorresponding hard-coded internet protocol (IP) address. A wirelessconnection may be used to decrease steps a pilot or user must take. Forexample, a portable device is not required to be plugged in anywhere onthe aircraft. In some embodiments, a wired connection such as auniversal serial bus (USB) connection is used. In the example shown,device 102 is not installed in the aircraft. Device 102 may comprise asmart phone, tablet, smart watch, or other IoT device. The device maycomprise an application designed to facilitate the data transfer andstore the collected data.

In some embodiments, device 102 is installed within the aircraft and theentire aircraft is transported to a location with a network connection.In some embodiments, flight recording device data is not transmitted toa separate device. The flight recording device comprises software thatperforms the internet check and facilitates data transfer.

FIG. 1B is a diagram illustrating an embodiment of data transfer from adevice to a network. In the example shown, flight data is uploaded fromdevice 102 to network 104. Device 102 may be transported to a locationwith an internet connection after it receives flight data from anaircraft. For example, the device is a personal device of the aircraftpilot. When the pilot returns to home, work, or a location with aninternet connection, the flight data is uploaded to an online network.In some embodiments, an application installed on the device enables theflight data to be synced to the network automatically.

Syncing to an online network may allow the flight data to be processedby a powerful processor or be analyzed together with data from otheraircraft. In some embodiments, the flight data is uploaded to an onlinenetwork where it is downloaded by a separate processor. In someembodiments, the flight data is analyzed on the online network, forexample by using online tools. In some embodiments, the flight data isuploaded via an internet connection to a processor that congregates andprocesses flight data for multiple aircraft. An aircraft company mayhave access to the online network or congregational processor. Theaircraft company may make decisions for future designs of the aircraftor provide advice to pilots based on the flight data.

FIG. 2A is a flow diagram illustrating an embodiment of a flight datacollection process. At 200, flight data is collected and stored onboardthe aircraft. Flight data is collected and stored on a “black box” orflight data recording device. The flight data recording device may storehigh resolution data. The flight data is stored on a computer memory. At201, a subset of the flight data to be saved is determined. A subset ofthe flight data recording device data is saved to a separate deviceeither installed in the aircraft or a portable device. In the event aseparate device is not used, a subset of flight data determined not tobe saved is deleted from the flight data recording device. At 202, asubset of the flight data is saved to a device (e.g. the separate deviceor the flight data recording device). The subset of the flight data maycomprise data that is of interest to a pilot or aircraft company. At204, the device is transported to a location with an internetconnection. At 206, the subset of the flight data is uploaded from thedevice to an online network. The flight data may be downloaded from theonline network and processed, with processed flight data uploaded backto the online network. In some embodiments, the flight data is processedon the network. At 208, processed flight data from the online network isreceived. The device may display processed flight data via anapplication installed on the device.

FIG. 2B is a flow diagram illustrating an embodiment of a flight datacollection process. At 250, flight data is received and stored. At 252,it is determined whether an internet connection is available. In theevent an internet connection is available, at 254 flight data istransmitted. The flight data may be packaged and sent, wherein packagingcomprises formatting or editing the data. The data may be sent to anonline network. After sending the flight data or in the event aninternet connection is not available, at 256 it is determined whetherflight data gathering is complete. For example, flight data istransmitted while the aircraft is mid-flight. Gathering is complete whenthe aircraft has completed flight. In the event flight data gathering isnot complete, the process returns to 250. In the event flight datagathering is complete, at 258 it is determined whether all flight datahas been transmitted. In the event an internet connection was notavailable during flight, the flight data may not have been sent at allor in entirety. In the event all flight data is sent, the process isfinished. In the event not all flight data is sent, the stored flightdata is maintained at 260. Maintaining the stored data may compriserefreshing the data or ensuring the data is not overwritten. At 262 itis determined whether an internet connection is available. In the eventan internet connection is not available, the stored flight data ismaintained until an internet connection is available. Intermittentinternet checks may be performed. In the event the internet connectionis available, at 264 flight data is packaged and sent and the process isfinished.

FIG. 2C is a flow diagram illustrating an embodiment of a flight datacollection process. In some embodiments, data transmission from theaircraft to an online network occurs solely after flight is complete.Flight data recorder activity is limited to data collection during thetime of flight. At 266, it is determined whether flight is complete. Inthe event flight is complete (e.g. the aircraft has landed), at 267flight data is received. Flight data is received in the event the flightdata recorder is not the uploading device. For example, a portabledevice or uploading device installed on the aircraft receives flightdata from a flight data recorder onboard the aircraft. At 268, it isdetermined whether an internet connection is available. In the event aninternet connection is available, at 270 flight data is transmitted andthe process is finished. The flight data is transmitted to an onlinenetwork. In the event an internet connection is not available, at 269the flight data is stored until it is determined that an internetconnection is available.

In various embodiments, the processes and connections described above aspertaining to aircraft pertain to other types of vehicles analogously.For example, vehicle data is considered rather than specifically flightdata. A vehicle data recorder is used rather than a flight datarecorder. Rather than determining whether a flight is complete, it isdetermined whether a vehicle trip is complete. In some embodiments,completion of a trip or flight is determined based on when a vehicle isturned on or off.

FIG. 2D is a flow diagram illustrating an embodiment of a vehicle datacollection process. At 272, vehicle data is received. The vehicle datamay be received from a vehicle data recorder in the event a seconddevice is used for uploading the vehicle data to an online network. Thevehicle data may be received from sensors and actuators in the event thevehicle data recorder is used to directly upload vehicle data. At 273,it is determined that an internet connection is not available. Thevehicle may travel through remote locations without connectivity. At274, the vehicle data is stored. For example, the vehicle data is storedon the vehicle data recorder or the second device. At 275, it isdetermined that an internet connection has become available. At 276, thevehicle data is transmitted based at least in part on the determinationthat an internet connection has become available.

FIG. 3 is a diagram illustrating an embodiment of onboard flight datacollection elements. In the example shown, aircraft 300 comprises flightdata recorder 302, flight computer 304, sensors 306, and aircraftcontrols 308. Flight data recorder 302 may record flight data at regularintervals (e.g. every half second) throughout flight. In someembodiments, the flight data recorder records data in faster intervalsin the event an abnormal change is detected. For example, if an extremechange in yaw is recorded, the flight data recorder may increase infrequency of recordings. The flight recorder may record actuatorpositions, pilot instructions, flight computer instructions, sensordata, engine information, time and date, or any other appropriate data.In the example shown, flight data recorder 302 receives inputs fromflight computer 304, sensors 306, and aircraft controls 308.

FIG. 4 is a flow diagram illustrating an embodiment of user actionsthroughout a vehicle data collection process. At 400, a vehicle trip iscompleted. At 402, a device is brought in proximity to the vehicle. Insome embodiments, the device comprises an application that sets up datato sync from a device onboard the vehicle to the device when the deviceis brought within a set distance from the vehicle and the vehicle isdetected to have completed a trip. The application determines whetherthe device onboard the vehicle has stored data that has not yet beenuploaded. In some embodiments, each trip is tracked with a unique tripnumber that is used to determine whether data has already been uploaded.For example, the trip number is incremented each time the vehicle isturned on. At 404, the device is brought to a location with an internetconnection. In some embodiments, the device comprises an applicationthat automatically uploads vehicle data from the device to specifiedonline network when the device is brought into a location with aninternet connection.

In some embodiments, a separate portable device is not used. Theuploading device may be installed in the vehicle. User (e.g. pilot ordriver) actions would comprise ending the trip in a location with aninternet connection or transporting the vehicle to a location with aninternet connection following trip completion.

FIG. 5 is a diagram illustrating an embodiment of a vehicle datacollection application. A vehicle data collection application mayprovide a simple interface for a user or passenger of the vehicle tocollect data from the vehicle and provide the data to an online network.In the example shown, device 500 comprises a display withconnected/disconnected button 502 and sync button 504. The buttons maycomprise virtual buttons that appear on the device screen. When using aseparate device from the vehicle data recording device,connected/disconnected button 502 may display “connected” when theseparate device is connected to a vehicle data recorder or storagedevice onboard the vehicle. “Connected” may let a pilot or customer knowthat the device is able to begin the data transfer. Button 502 maydisplay “disconnected” when the connection between the device and thevehicle is broken. For example, a portable device may be brought out ofrange for WiFi-direct or a cable connecting a separate device and anvehicle data recorder may be unplugged. In some embodiments, a userpresses sync button 504 when the device is connected to begin datatransfer from the vehicle to the device. In some embodiments, syncbutton 504 is pressed when the device is brought to a location with aninternet connection. Pressing the sync button in that environment maybegin data transfer from the device to an online network.

In various embodiments, the interface of the application takes differentforms. For example, the application may comprise a “fetch from vehicle”button or “upload to cloud” button.

An electronic recording device onboard the vehicle may comprise acorresponding application program interface (API), which is used intransferring data from the recording device to the upload device. Forexample, the electronic recording device may comprise a time seriesdatabase that has a corresponding API which allows a mobile phone orother smart device to access the data. An application on the mobilephone issues requests from the API to retrieve data. A separate databasemay be used on the portable device, such as a mobile database. Data istransferred from the mobile database to an online database, which alsohas a corresponding API. In some embodiments, a data visualization toolreads from the online database.

FIG. 6 is a diagram illustrating an embodiment of devices connected to anetwork. In the example shown, device_1 602, device_2 604, and device_3606 are connected to network 600. Multiple devices may upload vehicledata pertaining to multiple vehicles to a shared network. Processing mayoccur based on aggregated vehicle data. The aggregated vehicle data maybe used for the purposes of an vehicle company or provided to customersinterested in the vehicles. A vehicle company or other owner of theshared network may determine how to process the data or access to thedata.

FIG. 7 is a diagram illustrating an embodiment of a vehicle dataapplication displaying processed vehicle data. Processed vehicle datamay be provided to a device from the online network and displayed via anapplication. The application may comprise data collection and dataviewing or may be a separate application dedicated to data viewing andanalytics. For example, a user selects specific parameters to view invarious formats, such as graphs, charts, or tables. In the exampleshown, table 702 displays energy consumption during flight for anaircraft associated with device 700. Table 704 displays average energyconsumption during flight for all aircraft.

In some embodiments, a portable device may be associated with multiplevehicles. A data collection or data viewing application installed on thedevice may have a method of selecting a specific vehicle within theapplication. In various applications, various diagnostics are performedand provided based on the vehicle data.

In the event the data uploading device is a portable device notinstalled in the vehicle, the portable device may be a user's personaldevice. A data collection and/or data viewing application may berequired to be installed on the user's personal portable device. In someembodiments, the application may enable the portable device to act as akey that unlocks the vehicle, ensuring that the pilot has a device withthe corresponding application installed when embarking on a trip usingthe vehicle. The application may comprise features to encourage orensure a user syncs data to the online network. For example, theapplication may send reminders to a user or lock a user out of a vehicleif vehicle data has not been uploaded.

FIG. 8 is a flow diagram illustrating an embodiment of a data uploadprompt process. A first reminder is provided and then in the event thereminder is not followed up on, the vehicle is locked. At 800, it isdetermined whether vehicle data has been uploaded to the network withina set period of time. For example, the vehicle data may be required tobe uploaded within a few days of a trip. In the event vehicle data hasnot been uploaded to the network within a set period of time, at 802 areminder is sent to a device. The device may be a portable device,vehicle data recording device, or device installed on the vehicle thatis not the vehicle data recording device. A data collection applicationon the device may provide a reminder notification. At 804, it isdetermined whether vehicle data has been uploaded to the network withina set period of time since sending the reminder. In the event vehicledata has not been uploaded to the network within a set period of timesince sending the reminder, at 806 the user is locked from the vehicleuntil vehicle data is uploaded to the network. For example, anapplication on the device may be used as a virtual key. Withoutuploading the vehicle data, the application may prevent the vehicle fromstarting. In the event vehicle data has been uploaded (e.g. in theoriginal set period of time, following the reminder, or followinglock-out), at 808 it is determined whether the process is done. Forexample, the process is finished in the event the vehicle has not beentaken on more trips or all vehicle data has been uploaded. In the eventthe process is not done, subsequent iterations are carried out.

FIG. 9 is a diagram illustrating an embodiment of an aircraft. In someembodiments, the method for collecting data is used in a multicopterdesigned to fly over water. The aircraft may be typically landed onbodies of water, where an online or cellular connection may be lessprevalent. In the aircraft shown, fuselage 900 has two booms (916 and920) which pass through it, perpendicular to the fuselage. The boomsalso pass through floats 926 and 928, which are located on either sideof the fuselage. Rotors 912, 918, and 924 are positioned on float 926whereas rotors 902, 906, and 910 are positioned on float 928. Rotors 915and 904 are positioned on boom 916, on either side of the floats. Rotors908 and 922 are positioned on boom 920, on either side of the floats.The flight data collection method may be used to collect data on thrustsof the rotors, pitch of the aircraft, or any appropriate parameter.

In the event the disclosed method is executed on a portable IoT device,the vehicle may be designed around the device. For example, the vehiclecontrols may comprise a slot for a tablet or smart phone. Inserting thetablet or smart phone may unlock the vehicle.

Although the foregoing embodiments have been described in some detailfor purposes of clarity of understanding, the invention is not limitedto the details provided. There are many alternative ways of implementingthe invention. The disclosed embodiments are illustrative and notrestrictive.

What is claimed is:
 1. A vehicle data collection method, comprising:receiving vehicle data at a device on a vehicle during vehicleoperation; transmitting a first portion of the vehicle data, while thevehicle is in operation, based at least in part on a determination thatan internet connection is available; determining during vehicleoperation that the internet connection from the device to the internetis no longer available; storing a remaining portion of the vehicle dataon the device based at least in part on the determination that theinternet connection is no longer available; determining that a restoredinternet connection has become available; and transmitting the remainingportion of the vehicle data based at least in part on the determinationthat the restored internet connection has become available.
 2. Themethod of claim 1, wherein the device comprises a tablet, phone, orother portable connected device.
 3. The method of claim 1, wherein thedevice is installed on the vehicle.
 4. The method of claim 1, whereinthe device comprises a vehicle data recording device installed on thevehicle.
 5. The method of claim 1, wherein the vehicle data is receivedfrom a vehicle data recording device onboard the vehicle.
 6. The methodof claim 5, comprising determining a subset of received vehicle data tostore, wherein a subset of vehicle data received from the vehicle datarecording device is stored.
 7. The method of claim 5, wherein allreceived vehicle data is stored and received vehicle data comprises asubset of vehicle data saved on the vehicle data recording device. 8.The method of claim 1, wherein stored vehicle data comprises time seriesdata.
 9. The method of claim 1, wherein stored vehicle data comprisesaudio data, video data, or actuator parameters.
 10. The method of claim5, wherein the vehicle data is received over a Bluetooth connection,over a local area network, or in absence of an internet or cellularconnection.
 11. The method of claim 5, wherein the vehicle data isautomatically received and stored in the event the device is locatedwithin a threshold distance from a corresponding vehicle followingcompletion of flight.
 12. The method of claim 1, wherein stored vehicledata is transmitted to an online network, wherein vehicle datapertaining to multiple vehicles is uploaded to the online network. 13.The method of claim 1, further comprising receiving processed vehicledata.
 14. The method of claim 1, further comprising displaying processedvehicle data.
 15. The method of claim 1, comprising determining whethera connection to receive vehicle data is secured.
 16. The method of claim1, comprising determining to start or stop receiving vehicle data. 17.The method of claim 1, comprising determining to start or stoptransmitting vehicle data.
 18. The method of claim 1, further comprisingsending a prompt in the event stored vehicle data has not beentransmitted within a predetermined time from storing the vehicle data.19. The method of claim 1, further comprising preventing power on of avehicle in the event stored vehicle data has not been transmitted withina predetermined time from storing the vehicle data.
 20. A system forvehicle data collection, comprising: a vehicle; and a connected deviceconfigured to: receive vehicle data at a device on a vehicle duringvehicle operation; transmit a first set of vehicle data, while thevehicle is in operation, based at least in part on a determination thatan internet connection is available; determine that the internetconnection between the connected device and the internet is no longeravailable; store the vehicle data on the device based at least in parton the determination that the internet connection is no longeravailable; determine that a restored internet connection has becomeavailable; and transmit the vehicle data based at least in part on thedetermination that the restored internet connection has becomeavailable.